From 9f3cc5fcc4ee5d432fc991d022078bcbb86ed08f Mon Sep 17 00:00:00 2001 From: John Ericson Date: Thu, 14 Jul 2016 01:05:58 -0700 Subject: [PATCH] Better rational for build-dependencies and other kinds being disjoint. The old reason was bad because nothing prevents normal dependencies from being built before the build script. In fact this is a wanted feature. and if it is implemented the old reason would become invalid and confusing. --- src/doc/specifying-dependencies.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/src/doc/specifying-dependencies.md b/src/doc/specifying-dependencies.md index 03c4a9def..f78d667ee 100644 --- a/src/doc/specifying-dependencies.md +++ b/src/doc/specifying-dependencies.md @@ -384,7 +384,10 @@ manifest: gcc = "0.3" ``` -The build script **does not** have access to the dependencies listed in the -`dependencies` or `dev-dependencies` section (they’re not built yet!). All build -dependencies will also not be available to the package itself unless listed -under the `dependencies` section as well. +The build script **does not** have access to the dependencies listed +in the `dependencies` or `dev-dependencies` section. Build +dependencies will likewise not be available to the package itself +unless listed under the `dependencies` section as well. A package +itself and its build script are built separately, so their +dependencies need not coincide. Cargo is kept simpler and cleaner by +using independent dependencies for independent purposes. -- 2.30.2